Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 862-tree-1
name: 1499
tree-preservation-order: undefined
862-tpo-1
uprn
address-text
point: POINT (-0.971052 50.867007)
geometry: MULTIPOLYGON (((-0.971010 50.867003,-0.971012 50.867011,-0.971018 50.867019,-0.971027 50.867025,-0.971039 50.867029,-0.971052 50.867030,-0.971065 50.867029,-0.971077 50.867025,-0.971087 50.867019,-0.971093 50.867012,-0.971095 50.867003,-0.971093 50.866995,-0.971087 50.866988,-0.971078 50.866981,-0.971053 50.866976,-0.971040 50.866977,-0.971028 50.866981,-0.971018 50.866987,-0.971012 50.866994,-0.971010 50.867003)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL